Adding support for X-Dgraph-AuthToken header #248
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses the issue raised here (and originally in #224) by adding a new "Auth Token" setting to the "Extra Settings" tab in the server connection modal. The inputted value will then be sent as the
X-Dgraph-AuthToken
HTTP header on requests to the server.I'm not familar with the Ratel codebase, so it's possible that I've missed something! I've followed the same pattern used for the Slash API Key for consistency.
When I ran
./scripts/build.prod.sh
it made updates toyarn.lock
andpackage-lock.json
, however I presumed these changes should not be commited as this PR does not introduce any new depedencies.This change is
Ratel Preview: